All NedFox incoming and outgoing messages are XML based. We have messages available  for a number of data formats, which will be described here. If for a certain message type no message is described here, please let us know so we can update the documentation or even implement new messagetypes.

When a NedFox XML message is received by Retail3000, the first thing what will happen is an XSD validation of that message. When the XSD validation fails, the message will be rejected. When the validation is correct, it depends on the messagetype what will happen after retrieval. For example, orders can be created automatically from the received messages, but shipment messages need to be processed manually at the moment that goods arrive.

In every NedFox XML message is the same 'Envelope' part. This part looks like the Edifact envelope and contains source and destination information. When a message is dropped immediately in Retail3000, the Envelope part will not be read because routing is not required, the message has already been arrived. But NedFox XML messages can also be sent by Email or X400 to RetailLink, our message gateway. In that case, the Envelop is red by RetailLink to determine the source and destination numbers. In that case, the partynumbers in the envelope should be correct numbers, worldwide unique (so registered ag GS1) and known in RetailLink. Please contact our supportdesk for further information around partynumbers and EDI messaging.